Skip to content

CI: Test Pyarrow Less #46386

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 8 commits into from
Closed

Conversation

lithomas1
Copy link
Member

  • closes #xxxx (Replace xxxx with the Github issue number)
  • Tests added and passed if fixing a bug or adding a new feature
  • All code checks passed.
  • Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

CI has been really clogged w/ 2-3hr queue times.

Cut down on number of builds by only testing Pyarrow on one python version(if behavior is different based on Python version, that is pyarrow's problem).

If compat continues to be an issue in the future, I would suggest that pyarrow test a "pandas-dev" build, similar to our numpydev builds. I have added one of these builds to fastparquet in the past, and it seems to be effective as there haven't been any recent issues with new fastparquet versions breaking CI IIRC.

@lithomas1 lithomas1 added the CI Continuous Integration label Mar 17, 2022
@lithomas1 lithomas1 marked this pull request as ready for review March 23, 2022 15:31
- env_file: actions-38.yaml
pattern: "not single_cpu"
pyarrow_version: 5
name: "Min Pyarrow"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the min pyarrow is actually 1.0.1, better just to name this like "Pyarrow v5"

- env_file: actions-38.yaml
pattern: "not single_cpu"
pyarrow_version: 7
name: "Latest Pyarrow"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this eventually won't be the latest, similar better to name this "Pyarrow v7"

@lithomas1 lithomas1 marked this pull request as draft March 26, 2022 17:52
@github-actions
Copy link
Contributor

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

@github-actions github-actions bot added the Stale label Apr 26, 2022
@lithomas1 lithomas1 closed this May 2, 2022
@lithomas1 lithomas1 deleted the test-pyarrow-less branch May 2, 2022 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants